Refactor Invalid Token Context Error#607
Merged
PedroDiez merged 2 commits intocamaraproject:mainfrom Apr 8, 2026
Merged
Conversation
PedroDiez
requested review from
eric-murray,
jlurien,
patrice-conil and
rartych
as code owners
hdamker
previously approved these changes
Apr 6, 2026
hdamker
approved these changes
Apr 8, 2026
Contributor
Author
|
I merge this PR, so as it can be aligned for PR#606 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
This PR refactors Invalid Token Context Error, by modifying default message formulated for this error in
CAMARA_common.yaml. It is compliant with the Purpose of Issue #601 and associated PR #602, and provides some semantic about its scope. Also avoids any linter topic as currently reads "... is not consistent with access token."NOTE:
messageis not normative so this is a default message proposal any implementation can adapt to its specific scopeWhich issue(s) this PR fixes:
Partially Fixes #601
Does this PR introduce a breaking change?
Special notes for reviewers:
Minor Point Quick review
Changelog input
Additional documentation
This section can be blank.